Skip to content

[ExecuTorch][llm] Add source-transform and Meta-kernel tests for MoE op#21122

Open
digantdesai wants to merge 3 commits into
gh/digantdesai/72/basefrom
gh/digantdesai/72/head
Open

[ExecuTorch][llm] Add source-transform and Meta-kernel tests for MoE op#21122
digantdesai wants to merge 3 commits into
gh/digantdesai/72/basefrom
gh/digantdesai/72/head

Conversation

@digantdesai

@digantdesai digantdesai commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

[ghstack-poisoned]
@pytorch-bot

pytorch-bot Bot commented Jul 22, 2026

Copy link
Copy Markdown

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/21122

Note: Links to docs will display an error until the docs builds have been completed.

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

❌ 5 New Failures, 1 Unrelated Failure, 1 Unclassified Failure

As of commit 13289b9 with merge base bfed808 (image):

NEW FAILURES - The following jobs have failed:

  • Build Presets / apple (llm) / build (gh)
    Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/Users/runner/work/executorch/executorch/test-infra/.github/actions/check-disk-space'. Did you forget to run actions/checkout before running your local action?
  • Build Presets / apple (profiling) / build (gh)
    Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/Users/runner/work/executorch/executorch/test-infra/.github/actions/check-disk-space'. Did you forget to run actions/checkout before running your local action?
  • Build Presets / apple (pybind) / build (gh)
    Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/Users/runner/work/executorch/executorch/test-infra/.github/actions/check-disk-space'. Did you forget to run actions/checkout before running your local action?
  • pull / unittest-buck / linux / linux-job (gh)
    RuntimeError: Command docker exec -t 7addf2e54f69a93beb6ffc8e1d100425fc853e6a9da4da211eebde620373f064 /exec failed with exit code 3
  • trunk / changes (gh)
    API rate limit exceeded for installation. If you reach out to GitHub Support for help, please include the request ID 4C60:9946C:14F956C:48BAD20:6A61952F and timestamp 2026-07-23 04:14:39 UTC. For more on scraping GitHub and how it may affect your rights, please review our Terms of Service (https://docs.github.com/en/site-policy/github-terms/github-terms-of-service)

UNCLASSIFIED FAILURE - DrCI could not classify the following job because the workflow did not run on the merge base. The failure may be pre-existing on trunk or introduced by this PR:

  • Labeler / label (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
    API rate limit exceeded for installation. If you reach out to GitHub Support for help, please include the request ID 3BC1:29FBD5:F57B2A:FA3777:6A619526 and timestamp 2026-07-23 04:14:30 UTC. For more on scraping GitHub and how it may affect your rights, please review our Terms of Service (https://docs.github.com/en/site-policy/github-terms/github-terms-of-service)

BROKEN TRUNK - The following job failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@github-actions

Copy link
Copy Markdown

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

[ghstack-poisoned]
[ghstack-poisoned]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. meta-exported

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant